Skip to content

Update nodejs minimum requirements.#9333

Merged
sbc100 merged 5 commits intoincomingfrom
node_version
Aug 28, 2019
Merged

Update nodejs minimum requirements.#9333
sbc100 merged 5 commits intoincomingfrom
node_version

Conversation

@sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Aug 27, 2019

Also require nodejs checks to pass (unless EM_IGNORE_SANITY is set).

Fixes: #9332

Copy link
Member

@kripken kripken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like latest Ubuntu LTS (18.04, Bionic) has 8.10. I'm not comfortable going later than that, as it's a reasonably new version, and may be common on CI etc.

In fact I worry other plenty of people may be using previous LTS still, which has 4.2...

ChangeLog.md Outdated

Current Trunk
-------------
- Update minimum nodejs version from v4.1.1 for v12.0.0 (Current LTS)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit - no need to capitalize Current, unless there is some language reason I am not aware of?

@sbc100
Copy link
Collaborator Author

sbc100 commented Aug 27, 2019

Remember that most emsdk users are not effected here? Does that change anything for you?

I'll change this to 8.10.. hopefully that still gives us a lot of modern features. But in general I think supporting old version of node that developers might have installed doesn't need to be a goal of our does it? For non-emsdk users a simple "please upgrade node" message should be very easy to solve no?

Also require nodejs checks to pass (unless EM_IGNORE_SANITY is set).

Fixes: #9332
@kripken
Copy link
Member

kripken commented Aug 27, 2019

Yeah, asking users to upgrade node isn't so bad, especially if the emsdk installs a proper version. Still, I think supporting latest Ubuntu LTS might be convenient for users. And that version does have modern enough JS for using let etc.

Copy link
Member

@kripken kripken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm aside from that -O1/-O2 issue?

@sbc100 sbc100 merged commit 2b13f31 into incoming Aug 28, 2019
@sbc100 sbc100 deleted the node_version branch August 28, 2019 02:04
sbc100 added a commit that referenced this pull request Aug 28, 2019
We are reverting the emsdk node version bump so this needs to be
reverted too until we can reland.
sbc100 added a commit that referenced this pull request Aug 28, 2019
We reverted the emsdk node version bump,
(emscripten-core/emsdk#339, which means this
change also needs to be reverted too until we can reland.
sbc100 added a commit that referenced this pull request Aug 28, 2019
We reverted the emsdk node version bump,
(emscripten-core/emsdk#339, which means this
change also needs to be reverted too until we can reland.
belraquib pushed a commit to belraquib/emscripten that referenced this pull request Dec 23, 2020
Also require nodejs checks to pass (unless EM_IGNORE_SANITY is set).
belraquib pushed a commit to belraquib/emscripten that referenced this pull request Dec 23, 2020
…mscripten-core#9345)

We reverted the emsdk node version bump,
(emscripten-core/emsdk#339, which means this
change also needs to be reverted too until we can reland.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Require a recent node version and allow more recent JS features.

2 participants